Thanks.
Now that Java 25 has sailed, could we directly go to test on Java 26 ea?

Now that Java 25 has sailed, could we directly go to test on Java 26 ea?

Yes, of course. The current change was late anyways and is currently more a demo.
But before applying the update to Java-26 ea, I would like to complete the unification of build configuration first:

• [I/Y-Build] Unify build configurations into buildConfigurations.json #3402

with that all can be configured in one file (except for the fixes). But it should land soon.

Do you already have a plan when you start the Java-26 branch and need the new Y-build?

Now that Java 25 has sailed, could we directly go to test on Java 26 ea?

This is now done using the provided EA builds from https://jdk.java.net/26/, respectively the provided openjdk-java26 available by default in all Jenkins instances, provided by the EF infra team:

• https://github.com/eclipse-cbi/jiro/wiki/Tools-(JDK,-Maven,-Ant)#openjdk

If the latter is not sufficient it can also be changed to download from jdk.java.net.

Furthermore this include all the other steps to prepare the Y-builds for Java-26 BETA.
FYI @MohananRahul I took care of it for this time to demonstrate what to do (the next time it should be even easier as this also contains some fixes/clean-ups).

@stephan-herrmann please let me know if this is fine and when-ever you want the Java-26 BETA builds to start.
If it can wait for a little bit, I'll probably find some time to generally unify I- and Y-build tests further (which would reduce the changes in this PR).

@stephan-herrmann, @mpalat or @jarthana as also asked in Help Desk issue 6744, is the Y-build job for 4.37 still relevant or can I delete it?
If you don't need it anymore I could even delete it before the Y-build for 4.38 is activated.

@stephan-herrmann, @mpalat or @jarthana as also asked in Help Desk issue 6744, is the Y-build job for 4.37 still relevant or can I delete it? If you don't need it anymore I could even delete it before the Y-build for 4.38 is activated.

I'll consider no response as consent and will delete the Y-build job for 4.37 in the next days. As the beta branch for Java-26 is already created I assume it's really irrelevant now.
Or maybe @iloveeclipse can help here?

@stephan-herrmann, @mpalat or @jarthana as also asked in Help Desk issue 6744, is the Y-build job for 4.37 still relevant or can I delete it? If you don't need it anymore I could even delete it before the Y-build for 4.38 is activated.

I'll consider no response as consent and will delete the Y-build job for 4.37 in the next days. As the beta branch for Java-26 is already created I assume it's really irrelevant now. Or maybe @iloveeclipse can help here?

Sorry for late answer, my current focus is on master, not the next branch :)

I see no need for keeping any Y-build job beyond the point where changes have been merged from the BETA branch into master. At that point we have the last P and Y builds for consumers of the latest SDK release, and we have fresh I-builds for early adopters.

Sorry for late answer, my current focus is on master, not the next branch :)

I see no need for keeping any Y-build job beyond the point where changes have been merged from the BETA branch into master. At that point we have the last P and Y builds for consumers of the latest SDK release, and we have fresh I-builds for early adopters.

Thank you for the clearification. Then I'll proceed with deleting these jobs tomorrow.
In general, if really necessary, they are also not too dificult to restore.